An import package is a set of documents contained in an archive (ZIP) file and an accompanying MS Excel workbook that contains metadata about the package documents. Import packages support external references, hybrid documents, multiple revisions of the same document, and drawing title block data exchange.
Import packages are similar to briefcases but are more powerful. However, the two are not interchangeable. Packages can be exported from Meridian Explorer as described in
One way that packages are different from briefcases is that you import packages into Meridian Enterprise according to a set of rules called an import profile that is created by a system administrator. Different import profiles can be configured for different sources, destinations, or purposes for the packages.
Meridian Enterprise Server also lets you see how documents will be imported before the import is actually performed. This is done by first scanning the package. This lets you verify the import configuration before any changes are made in the destination vault.
Meridian Enterprise Server scans and imports packages in the background, which lets you continue working. You can monitor the progress of an import at any time.
The following table lists the minimum steps for importing a package and the corresponding topics in this guide that describe each step in more detail. The steps are listed in the order that they should be performed.
| No. | Step | Topic |
|---|---|---|
|
1 |
Collect the documents into a folder or in an archive (ZIP) file that you want to import. |
|
| 2 |
Create an MS Excel workbook file that includes a worksheet that contains the metadata that you want to import. |
|
|
3 |
Create a copy of the workbook file with empty rows to serve as a pattern for the metadata. |
|
| 4 |
|
|
|
5 |
Create a new, open package to associate the source documents, metadata, and import profile together for import. |
|
| 6 | Start the scanning process. | Scanning an import package |
|
7 |
Review the scanning results and adjust the import actions as necessary. |
|
| 8 | Start the document import process. | Importing an import package |
|
9 |
Close the package to indicate that it has been completed. |
Depending on the outcome of the scanning or import processes or for business reasons, you might want to repeat, abort, or skip steps. The preceding steps and the available commands for each step are shown in Routing an import package and are available in the toolbar.
Import packages are designed so that these steps can be performed by different users who may have separate responsibilities for documents in your organization. For example, one user (such as a system administrator) might be responsible for creating import profiles; a second user (such as a project team member) for creating, scanning, and importing packages; and a third user (such as a project leader) for approving packages before they are imported and for closing packages. Processes like this can be supported by the security privileges described in Creating an import profile.
The following topics describe these steps.
Related tasks